<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Software design pattern</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Software_design_pattern"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Software_design_pattern rootpage-Software_design_pattern skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Software design pattern</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">
<p>In <a href="Software_engineering" title="Software engineering">software engineering</a>, a <b>software design pattern</b> or <b>design pattern</b> is a general, <a href="Reusability" title="Reusability">reusable</a> solution to a commonly occurring problem in many contexts in <a href="Software_design" title="Software design">software design</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> A design pattern is not a rigid structure to be transplanted directly into <a href="Source_code" title="Source code">source code</a>. Rather, it is a description or a template for solving a particular type of problem that can be deployed in many different situations.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> Design patterns can be viewed as formalized <a href="Best_practice" title="Best practice">best practices</a> that the programmer may use to solve common problems when designing a software application or system.
</p><p><a href="Object-oriented_programming" title="Object-oriented programming">Object-oriented</a> design patterns typically show relationships and interactions between <a href="Class_(computer_science)" class="mw-redirect" title="Class (computer science)">classes</a> or <a href="Object_(computer_science)" title="Object (computer science)">objects</a>, without specifying the final application classes or objects that are involved. Patterns that imply mutable state may be unsuited for <a href="Functional_programming" title="Functional programming">functional programming</a> languages. Some patterns can be rendered unnecessary in languages that have built-in support for solving the problem they are trying to solve, and object-oriented patterns are not necessarily suitable for non-object-oriented languages.
</p><p>Design patterns may be viewed as a structured approach to <a href="Computer_programming" title="Computer programming">computer programming</a> intermediate between the levels of a <a href="Programming_paradigm" title="Programming paradigm">programming paradigm</a> and a concrete <a href="Algorithm" title="Algorithm">algorithm</a>.
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>
<p>Patterns originated as an <a href="Pattern_(architecture)" title="Pattern (architecture)">architectural concept</a> by <a href="Christopher_Alexander" title="Christopher Alexander">Christopher Alexander</a> as early as 1977 in <a href="A_Pattern_Language" title="A Pattern Language">A Pattern Language</a> (cf. his article, "The Pattern of Streets," JOURNAL OF THE AIP, September, 1966, Vol. 32, No. 5, pp. 273–278). In 1987, <a href="Kent_Beck" title="Kent Beck">Kent Beck</a> and <a href="Ward_Cunningham" title="Ward Cunningham">Ward Cunningham</a> began experimenting with the idea of applying patterns to programming – specifically <a href="Pattern_language" title="Pattern language">pattern languages</a> – and presented their results at the <a href="OOPSLA" title="OOPSLA">OOPSLA</a> conference that year.<sup id="cite_ref-Smith1987_3-0" class="reference"><a href="#cite_note-Smith1987-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Beck1987_4-0" class="reference"><a href="#cite_note-Beck1987-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> In the following years, Beck, Cunningham and others followed up on this work.
</p><p>Design patterns gained popularity in <a href="Computer_science" title="Computer science">computer science</a> after the book <a href="Design_Patterns" title="Design Patterns"><i>Design Patterns: Elements of Reusable Object-Oriented Software</i></a> was published in 1994 by the so-called "Gang of Four" (Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides), which is frequently abbreviated as "GoF". That same year, the first <a href="Pattern_Languages_of_Programming" class="mw-redirect" title="Pattern Languages of Programming">Pattern Languages of Programming</a> Conference was held, and the following year the <a href="Portland_Pattern_Repository" title="Portland Pattern Repository">Portland Pattern Repository</a> was set up for documentation of design patterns. The scope of the term remains a matter of dispute. Notable books in the design pattern genre include:
</p>
<ul><li><style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */
.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}
/* end https://en.wikipedia.org/ */
</style><cite id="CITEREFGammaHelmJohnsonVlissides1994" class="citation book cs1"><a href="Erich_Gamma" title="Erich Gamma">Gamma, Erich</a>; <a href="Richard_Helm" title="Richard Helm">Helm, Richard</a>; <a href="Ralph_Johnson_(computer_scientist)" title="Ralph Johnson (computer scientist)">Johnson, Ralph</a>; <a href="John_Vlissides" title="John Vlissides">Vlissides, John</a> (1994). <a href="Design_Patterns_(book)" class="mw-redirect" title="Design Patterns (book)"><i>Design Patterns: Elements of Reusable Object-Oriented Software</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-63361-0</bdi>.</cite></li>
<li><cite id="CITEREFBrinch_Hansen1995" class="citation book cs1"><a href="Per_Brinch_Hansen" title="Per Brinch Hansen">Brinch Hansen, Per</a> (1995). <i>Studies in Computational Science: Parallel Programming Paradigms</i>. Prentice Hall. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-439324-7</bdi>.</cite></li>
<li><cite id="CITEREFBuschmannMeunierRohnertSommerlad1996" class="citation book cs1">Buschmann, Frank; Meunier, Regine; Rohnert, Hans; Sommerlad, Peter (1996). <i>Pattern-Oriented Software Architecture, Volume 1: A System of Patterns</i>. John Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-471-95869-7</bdi>.</cite></li>
<li><cite id="CITEREFBeck1997" class="citation book cs1"><a href="Kent_Beck" title="Kent Beck">Beck, Kent</a> (1997). <i>Smalltalk Best Practice Patterns</i>. Prentice Hall. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0134769042</bdi>.</cite></li>
<li><cite id="CITEREFSchmidtStalRohnertBuschmann2000" class="citation book cs1"><a href="Douglas_C._Schmidt" title="Douglas C. Schmidt">Schmidt, Douglas C.</a>; Stal, Michael; Rohnert, Hans; Buschmann, Frank (2000). <i>Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects</i>. John Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-471-60695-6</bdi>.</cite></li>
<li><cite id="CITEREFFowler2002" class="citation book cs1"><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a> (2002). <i>Patterns of Enterprise Application Architecture</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-12742-6</bdi>.</cite></li>
<li><cite id="CITEREFHohpeWoolf2003" class="citation book cs1">Hohpe, Gregor; Woolf, Bobby (2003). <a href="Enterprise_Integration_Patterns" title="Enterprise Integration Patterns"><i>Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-20068-6</bdi>.</cite></li>
<li><cite id="CITEREFFreemanRobsonBatesSierra2004" class="citation book cs1">Freeman, Eric T.; Robson, Elisabeth; Bates, Bert; <a href="Kathy_Sierra" title="Kathy Sierra">Sierra, Kathy</a> (2004). <i>Head First Design Patterns</i>. <a href="O'Reilly_Media" title="O'Reilly Media">O'Reilly Media</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-596-00712-6</bdi>.</cite></li>
<li><cite id="CITEREFLarman2004" class="citation book cs1"><a href="Craig_Larman" title="Craig Larman">Larman, Craig</a> (2004). <i>Applying UML and Patterns (3rd Ed, 1st Ed 1995)</i>. Pearson. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0131489066</bdi>.</cite></li></ul>
<p>Although design patterns have been applied practically for a long time, formalization of the concept of design patterns languished for several years.<sup id="cite_ref-Baroni2003_5-0" class="reference"><a href="#cite_note-Baroni2003-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Practice">Practice</h2></div>
<p>Design patterns can speed up the development process by providing proven development paradigms.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> Effective software design requires considering issues that may not become apparent until later in the implementation. Freshly written code can often have hidden, subtle issues that take time to be detected; issues that sometimes can cause major problems down the road. Reusing design patterns can help to prevent such issues,<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> and enhance code readability for those familiar with the patterns.
</p><p>Software design techniques are difficult to apply to a broader range of problems. Design patterns provide general solutions, <a href="Documentation" title="Documentation">documented</a> in a format that does not require specifics tied to a particular problem.
</p><p>In 1996, Christopher Alexander was invited to give a <a rel="nofollow" class="external text" href="https://www.patternlanguage.com/archive/ieee.html">Keynote Speech</a> to the 1996 OOPSLA Convention. Here he reflected on how his work on Patterns in Architecture had developed and his hopes for how the Software Design community could help Architecture extend Patterns to create living structures that use generative schemes that are more like computer code.
</p>
<div class="mw-heading mw-heading2"><h2 id="Motif">Motif</h2></div>
<p>A pattern describes a <i>design motif</i>, a.k.a. <i>prototypical micro-architecture</i>, as a set of program constituents (e.g., classes, methods...) and their relationships. A developer adapts the motif to their codebase to solve the problem described by the pattern. The resulting code has structure and organization similar to the chosen motif.
</p>
<div class="mw-heading mw-heading2"><h2 id="Domain-specific_patterns">Domain-specific patterns</h2></div>
<p>Efforts have also been made to codify design patterns in particular domains, including the use of existing design patterns as well as domain-specific design patterns. Examples include <a href="User_interface" title="User interface">user interface</a> design patterns,<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> <a href="Information_visualization" class="mw-redirect" title="Information visualization">information visualization</a>,<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> secure design,<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> "secure usability",<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> Web design <sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> and business model design.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup>
</p><p>The annual <a href="Pattern_Languages_of_Programming" class="mw-redirect" title="Pattern Languages of Programming">Pattern Languages of Programming</a> Conference proceedings <sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> include many examples of domain-specific patterns.
</p>
<div class="mw-heading mw-heading2"><h2 id="Object-oriented_programming">Object-oriented programming</h2></div>
<p><a href="Object-oriented_programming" title="Object-oriented programming">Object-oriented</a> design patterns typically show relationships and interactions between <a href="Class_(computer_science)" class="mw-redirect" title="Class (computer science)">classes</a> or <a href="Object_(computer_science)" title="Object (computer science)">objects</a>, without specifying the final application classes or objects that are involved. Patterns that imply mutable state may be unsuited for <a href="Functional_programming" title="Functional programming">functional programming</a> languages. Some patterns can be rendered unnecessary in languages that have built-in support for solving the problem they are trying to solve, and object-oriented patterns are not necessarily suitable for non-object-oriented languages.
</p>
<div class="mw-heading mw-heading2"><h2 id="Examples">Examples</h2></div>
<p>Design patterns can be organized into groups based on what kind of problem they solve. <a href="Creational_pattern" title="Creational pattern">Creational patterns</a> create objects. <a href="Structural_pattern" title="Structural pattern">Structural patterns</a> organize classes and objects to form larger structures that provide new functionality. <a href="Behavioral_pattern" title="Behavioral pattern">Behavioral patterns</a> describe collaboration between objects.
</p>
<div class="mw-heading mw-heading3"><h3 id="Creational_patterns"><a href="Creational_patterns" class="mw-redirect" title="Creational patterns">Creational patterns</a></h3></div>
<table class="wikitable">
<tbody><tr>
<th>Name
</th>
<th>Description
</th>
<th>In <i><a href="Design_Patterns" title="Design Patterns">Design Patterns</a></i>
</th>
<th>In <i><a href="Code_Complete" title="Code Complete">Code Complete</a></i><sup id="cite_ref-McConnell2004_15-0" class="reference"><a href="#cite_note-McConnell2004-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>
</th>
<th>Other
</th></tr>
<tr>
<td><a href="Abstract_factory" class="mw-redirect" title="Abstract factory">Abstract factory</a>
</td>
<td>Provide an interface for creating <i>families</i> of related or dependent objects without specifying their concrete classes.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Builder_pattern" title="Builder pattern">Builder</a>
</td>
<td>Separate the construction of a complex object from its representation, allowing the same construction process to create various representations.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Dependency_Injection" class="mw-redirect" title="Dependency Injection">Dependency Injection</a>
</td>
<td>A class accepts the objects it requires from an injector instead of creating the objects directly.
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Factory_method" class="mw-redirect" title="Factory method">Factory method</a>
</td>
<td>Define an interface for creating a <i>single</i> object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Lazy_initialization" title="Lazy initialization">Lazy initialization</a>
</td>
<td>Tactic of delaying the creation of an object, the calculation of a value, or some other expensive process until the first time it is needed. This pattern appears in the GoF catalog as "virtual proxy", an implementation strategy for the <a href="Proxy_pattern" title="Proxy pattern">Proxy</a> pattern.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes"><abbr title="Patterns of Enterprise Application Architecture">PoEAA</abbr><sup id="cite_ref-PoEAA_16-0" class="reference"><a href="#cite_note-PoEAA-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td><a href="Multiton" class="mw-redirect" title="Multiton">Multiton</a>
</td>
<td>Ensure a class has only named instances, and provide a global point of access to them.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Object_pool" class="mw-redirect" title="Object pool">Object pool</a>
</td>
<td>Avoid expensive acquisition and release of resources by recycling objects that are no longer in use. Can be considered a generalisation of <a href="Connection_pool" title="Connection pool">connection pool</a> and <a href="Thread_pool" title="Thread pool">thread pool</a> patterns.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Prototype_pattern" title="Prototype pattern">Prototype</a>
</td>
<td>Specify the kinds of objects to create using a prototypical instance, and create new objects from the 'skeleton' of an existing object, thus boosting performance and keeping memory footprints to a minimum.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Resource_acquisition_is_initialization" title="Resource acquisition is initialization">Resource acquisition is initialization</a> (RAII)
</td>
<td>Ensure that resources are properly released by tying them to the lifespan of suitable objects.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Singleton_pattern" title="Singleton pattern">Singleton</a>
</td>
<td>Ensure a class has only one instance, and provide a global point of access to it.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td>LivinGrimoire
</td>
<td>modularly absorbs skills(features/abilities) with one line of code per skill
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://github.com/yotamarker/LivinGrimoire/wiki">"LivinGrimoire software pattern"</a>. <i>GitHub</i>.</cite>
</td></tr></tbody></table>
<div class="mw-heading mw-heading3"><h3 id="Structural_patterns"><a href="Structural_pattern" title="Structural pattern">Structural patterns</a></h3></div>
<table class="wikitable">
<tbody><tr>
<th>Name
</th>
<th>Description
</th>
<th>In <i><a href="Design_Patterns" title="Design Patterns">Design Patterns</a></i>
</th>
<th>In <i><a href="Code_Complete" title="Code Complete">Code Complete</a></i><sup id="cite_ref-McConnell2004_15-1" class="reference"><a href="#cite_note-McConnell2004-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>
</th>
<th>Other
</th></tr>
<tr>
<td><a href="Adapter_pattern" title="Adapter pattern">Adapter</a>, Wrapper, or Translator
</td>
<td>Convert the interface of a class into another interface clients expect. An adapter lets classes work together that could not otherwise because of incompatible interfaces. The enterprise integration pattern equivalent is the translator.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Bridge_pattern" title="Bridge pattern">Bridge</a>
</td>
<td>Decouple an abstraction from its implementation allowing the two to vary independently.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Composite_pattern" title="Composite pattern">Composite</a>
</td>
<td>Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Decorator_pattern" title="Decorator pattern">Decorator</a>
</td>
<td>Attach additional responsibilities to an object dynamically keeping the same interface. Decorators provide a flexible alternative to subclassing for extending functionality.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Delegation_pattern" title="Delegation pattern">Delegation</a>
</td>
<td>Extend a class by composition instead of subclassing. The object handles a request by delegating to a second object (the delegate)
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td>Extension object
</td>
<td>Adding functionality to a hierarchy without changing the hierarchy.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Facade_pattern" title="Facade pattern">Facade</a>
</td>
<td>Provide a unified interface to a set of interfaces in a subsystem. Facade defines a higher-level interface that makes the subsystem easier to use.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Flyweight_pattern" title="Flyweight pattern">Flyweight</a>
</td>
<td>Use sharing to support large numbers of similar objects efficiently.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Front_controller" title="Front controller">Front controller</a>
</td>
<td>The pattern relates to the design of Web applications. It provides a centralized entry point for handling requests.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">
<p><abbr title="Core J2EE Patterns: Best Practices and Design Strategies (2nd Edition)">J2EE Patterns</abbr><sup id="cite_ref-J2EE_Patterns_17-0" class="reference"><a href="#cite_note-J2EE_Patterns-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>
<abbr title="Patterns of Enterprise Application Architecture">PoEAA</abbr><sup id="cite_ref-PoEAA2_18-0" class="reference"><a href="#cite_note-PoEAA2-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup>
</p>
</td></tr>
<tr>
<td><a href="Marker_interface_pattern" title="Marker interface pattern">Marker</a>
</td>
<td>Empty interface to associate metadata with a class.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes"><a href="Joshua_Bloch" title="Joshua Bloch">Effective Java</a><sup id="cite_ref-EffectiveJava_19-0" class="reference"><a href="#cite_note-EffectiveJava-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td><a href="Module_pattern" title="Module pattern">Module</a>
</td>
<td>Group several related elements, such as classes, singletons, methods, globally used, into a single conceptual entity.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Proxy_pattern" title="Proxy pattern">Proxy</a>
</td>
<td>Provide a surrogate or placeholder for another object to control access to it.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Twin_pattern" title="Twin pattern">Twin</a><sup id="cite_ref-20" class="reference"><a href="#cite_note-20"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup>
</td>
<td>Twin allows modeling of multiple inheritance in programming languages that do not support this feature.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr></tbody></table>
<div class="mw-heading mw-heading3"><h3 id="Behavioral_patterns"><a href="Behavioral_patterns" class="mw-redirect" title="Behavioral patterns">Behavioral patterns</a></h3></div>
<table class="wikitable">
<tbody><tr>
<th>Name
</th>
<th>Description
</th>
<th>In <i><a href="Design_Patterns" title="Design Patterns">Design Patterns</a></i>
</th>
<th>In <i><a href="Code_Complete" title="Code Complete">Code Complete</a></i><sup id="cite_ref-McConnell2004_15-2" class="reference"><a href="#cite_note-McConnell2004-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>
</th>
<th>Other
</th></tr>
<tr>
<td><a href="Blackboard_(design_pattern)" title="Blackboard (design pattern)">Blackboard</a>
</td>
<td><a href="Artificial_intelligence" title="Artificial intelligence">Artificial intelligence</a> pattern for combining disparate sources of data (see <a href="Blackboard_system" title="Blackboard system">blackboard system</a>)
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Chain-of-responsibility_pattern" title="Chain-of-responsibility pattern">Chain of responsibility</a>
</td>
<td>Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Command_pattern" title="Command pattern">Command</a>
</td>
<td>Encapsulate a request as an object, thereby allowing for the parameterization of clients with different requests, and the queuing or logging of requests. It also allows for the support of undoable operations.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Fluent_interface" title="Fluent interface">Fluent interface</a>
</td>
<td>Design an API to be method chained so that it reads like a DSL. Each method call returns a context through which the next logical method call(s) are made available.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Interpreter_pattern" title="Interpreter pattern">Interpreter</a>
</td>
<td>Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Iterator_pattern" title="Iterator pattern">Iterator</a>
</td>
<td>Provide a way to access the elements of an <a href="Aggregate_pattern" title="Aggregate pattern">aggregate</a> object sequentially without exposing its underlying representation.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Mediator_pattern" title="Mediator pattern">Mediator</a>
</td>
<td>Define an object that encapsulates how a set of objects interact. Mediator promotes <a href="Loose_coupling" title="Loose coupling">loose coupling</a> by keeping objects from referring to each other explicitly, and it allows their interaction to vary independently.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Memento_pattern" title="Memento pattern">Memento</a>
</td>
<td>Without violating encapsulation, capture and externalize an object's internal state allowing the object to be restored to this state later.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Null_object" class="mw-redirect" title="Null object">Null object</a>
</td>
<td>Avoid null references by providing a default object.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Observer_pattern" title="Observer pattern">Observer</a> or <a href="Publish/subscribe" class="mw-redirect" title="Publish/subscribe">Publish/subscribe</a>
</td>
<td>Define a one-to-many dependency between objects where a state change in one object results in all its dependents being notified and updated automatically.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Design_pattern_Servant" class="mw-redirect" title="Design pattern Servant">Servant</a>
</td>
<td>Define common functionality for a group of classes. The servant pattern is also frequently called helper class or utility class implementation for a given set of classes. The helper classes generally have no objects hence they have all static methods that act upon different kinds of class objects.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Specification_pattern" title="Specification pattern">Specification</a>
</td>
<td>Recombinable <a href="Business_logic" title="Business logic">business logic</a> in a <a href="Boolean_algebra" title="Boolean algebra">Boolean</a> fashion.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="State_pattern" title="State pattern">State</a>
</td>
<td>Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Strategy_pattern" title="Strategy pattern">Strategy</a>
</td>
<td>Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Template_method" class="mw-redirect" title="Template method">Template method</a>
</td>
<td>Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr>
<tr>
<td><a href="Visitor_pattern" title="Visitor pattern">Visitor</a>
</td>
<td>Represent an operation to be performed on instances of a set of classes. Visitor lets a new operation be defined without changing the classes of the elements on which it operates.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td></tr></tbody></table>
<div class="mw-heading mw-heading3"><h3 id="Concurrency_patterns"><a href="Concurrency_patterns" class="mw-redirect" title="Concurrency patterns">Concurrency patterns</a></h3></div>
<table class="wikitable">
<tbody><tr>
<th>Name
</th>
<th>Description
</th>
<th>In <i><a href="Pattern-Oriented_Software_Architecture" title="Pattern-Oriented Software Architecture">POSA2</a></i><sup id="cite_ref-POSA2_21-0" class="reference"><a href="#cite_note-POSA2-21"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup>
</th>
<th>Other
</th></tr>
<tr>
<td><a href="Active_Object" class="mw-redirect" title="Active Object">Active Object</a>
</td>
<td>Decouples method execution from method invocation that reside in their own thread of control. The goal is to introduce concurrency, by using <a href="Asynchronous_method_invocation" title="Asynchronous method invocation">asynchronous method invocation</a> and a <a href="Scheduling_(computing)" title="Scheduling (computing)">scheduler</a> for handling requests.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Balking_pattern" title="Balking pattern">Balking</a>
</td>
<td>Only execute an action on an object when the object is in a particular state.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Binding_properties_pattern" title="Binding properties pattern">Binding properties</a>
</td>
<td>Combining multiple observers to force properties in different objects to be synchronized or coordinated in some way.<sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup>
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Compute_kernel" title="Compute kernel">Compute kernel</a>
</td>
<td>The same calculation many times in parallel, differing by integer parameters used with non-branching pointer math into shared arrays, such as <a href="GPU" class="mw-redirect" title="GPU">GPU</a>-optimized <a href="Matrix_multiplication" title="Matrix multiplication">Matrix multiplication</a> or <a href="Convolutional_neural_network" title="Convolutional neural network">Convolutional neural network</a>.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Double-checked_locking" title="Double-checked locking">Double-checked locking</a>
</td>
<td>Reduce the overhead of acquiring a lock by first testing the locking criterion (the 'lock hint') in an unsafe manner; only if that succeeds does the actual locking logic proceed.
<p>Can be unsafe when implemented in some language/hardware combinations. It can therefore sometimes be considered an <a href="Anti-pattern" title="Anti-pattern">anti-pattern</a>.
</p>
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Event-Based_Asynchronous_Pattern" class="mw-redirect" title="Event-Based Asynchronous Pattern">Event-based asynchronous</a>
</td>
<td>Addresses problems with the asynchronous pattern that occur in multithreaded programs.<sup id="cite_ref-PC#2008_23-0" class="reference"><a href="#cite_note-PC#2008-23"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup>
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Guarded_suspension" title="Guarded suspension">Guarded suspension</a>
</td>
<td>Manages operations that require both a lock to be acquired and a precondition to be satisfied before the operation can be executed.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Join-pattern" title="Join-pattern">Join</a>
</td>
<td>Join-pattern provides a way to write concurrent, parallel and distributed programs by message passing. Compared to the use of threads and locks, this is a high-level programming model.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Lock_(computer_science)" title="Lock (computer science)">Lock</a>
</td>
<td>One thread puts a "lock" on a resource, preventing other threads from accessing or modifying it.<sup id="cite_ref-24" class="reference"><a href="#cite_note-24"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup>
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">PoEAA<sup id="cite_ref-PoEAA_16-1" class="reference"><a href="#cite_note-PoEAA-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td><a href="Messaging_pattern" title="Messaging pattern">Messaging design pattern (MDP)</a>
</td>
<td>Allows the interchange of information (i.e. messages) between components and applications.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Monitor_(synchronization)" title="Monitor (synchronization)">Monitor object</a>
</td>
<td>An object whose methods are subject to <a href="Mutual_exclusion" title="Mutual exclusion">mutual exclusion</a>, thus preventing multiple objects from erroneously trying to use it at the same time.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Reactor_pattern" title="Reactor pattern">Reactor</a>
</td>
<td>A reactor object provides an asynchronous interface to resources that must be handled synchronously.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Read-write_lock" class="mw-redirect" title="Read-write lock">Read-write lock</a>
</td>
<td>Allows concurrent read access to an object, but requires exclusive access for write operations. An underlying semaphore might be used for writing, and a <a href="Copy-on-write" title="Copy-on-write">Copy-on-write</a> mechanism may or may not be used.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Scheduler_pattern" class="mw-redirect" title="Scheduler pattern">Scheduler</a>
</td>
<td>Explicitly control when threads may execute single-threaded code.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td>Service handler pattern
</td>
<td>For each request, a server spawns a dedicated client handler to handle a request.<sup id="cite_ref-25" class="reference"><a href="#cite_note-25"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup> Also referred to as <i>thread-per-session</i>.<sup id="cite_ref-26" class="reference"><a href="#cite_note-26"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup>
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Thread_pool" title="Thread pool">Thread pool</a>
</td>
<td>A number of threads are created to perform a number of tasks, which are usually organized in a queue. Typically, there are many more tasks than threads. Can be considered a special case of the <a href="Object_pool" class="mw-redirect" title="Object pool">object pool</a> pattern.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td><a href="Thread-specific_storage" class="mw-redirect" title="Thread-specific storage">Thread-specific storage</a>
</td>
<td>Static or "global" memory local to a thread.
</td>
<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td>Safe Concurrency with Exclusive Ownership
</td>
<td>Avoiding the need for runtime concurrent mechanisms, because exclusive ownership can be proven. This is a notable capability of the Rust language, but compile-time checking isn't the only means, a programmer will often manually design such patterns into code - omitting the use of locking mechanism because the programmer assesses that a given variable is never going to be concurrently accessed.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr>
<tr>
<td>CPU atomic operation
</td>
<td>x86 and other CPU architectures support a range of atomic instructions that guarantee memory safety for modifying and accessing primitive values (integers). For example, two threads may both increment a counter safely. These capabilities can also be used to implement the mechanisms for other concurrency patterns as above. The <a href="C_Sharp_(programming_language)" title="C Sharp (programming language)">C#</a> language uses the <a rel="nofollow" class="external text" href="https://docs.microsoft.com/en-us/dotnet/api/system.threading.interlocked?view=net-5.0">Interlocked</a> class for these capabilities.
</td>
<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No
</td>
<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">—
</td></tr></tbody></table>
<div class="mw-heading mw-heading2"><h2 id="Documentation">Documentation</h2></div>
<p>The documentation for a design pattern describes the context in which the pattern is used, the forces within the context that the pattern seeks to resolve, and the suggested solution.<sup id="cite_ref-GabrielHillside_27-0" class="reference"><a href="#cite_note-GabrielHillside-27"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup> There is no single, standard format for documenting design patterns. Rather, a variety of different formats have been used by different pattern authors. However, according to <a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Martin Fowler</a>, certain pattern forms have become more well-known than others, and consequently become common starting points for new pattern-writing efforts.<sup id="cite_ref-Fowler2006_28-0" class="reference"><a href="#cite_note-Fowler2006-28"><span class="cite-bracket">[</span>28<span class="cite-bracket">]</span></a></sup> One example of a commonly used documentation format is the one used by <a href="Erich_Gamma" title="Erich Gamma">Erich Gamma</a>, <a href="Richard_Helm" title="Richard Helm">Richard Helm</a>, <a href="Ralph_Johnson_(computer_scientist)" title="Ralph Johnson (computer scientist)">Ralph Johnson</a>, and <a href="John_Vlissides" title="John Vlissides">John Vlissides</a> in their book <i><a href="Design_Patterns" title="Design Patterns">Design Patterns</a></i>. It contains the following sections:
</p>
<ul><li><b>Pattern Name and Classification:</b> A descriptive and unique name that helps in identifying and referring to the pattern.</li>
<li><b>Intent:</b> A description of the goal behind the pattern and the reason for using it.</li>
<li><b>Also Known As:</b> Other names for the pattern.</li>
<li><b>Motivation (Forces):</b> A scenario consisting of a problem and a context in which this pattern can be used.</li>
<li><b>Applicability:</b> Situations in which this pattern is usable; the context for the pattern.</li>
<li><b>Structure:</b> A graphical representation of the pattern. <a href="Unified_Modeling_Language#UML_Class_Diagram" title="Unified Modeling Language">Class diagrams</a> and <a href="Interaction_diagram" class="mw-redirect" title="Interaction diagram">Interaction diagrams</a> may be used for this purpose.</li>
<li><b>Participants:</b> A listing of the classes and objects used in the pattern and their roles in the design.</li>
<li><b>Collaboration:</b> A description of how classes and objects used in the pattern interact with each other.</li>
<li><b>Consequences:</b> A description of the results, side effects, and trade offs caused by using the pattern.</li>
<li><b>Implementation:</b> A description of an implementation of the pattern; the solution part of the pattern.</li>
<li><b>Sample Code:</b> An illustration of how the pattern can be used in a programming language.</li>
<li><b>Known Uses:</b> Examples of real usages of the pattern.</li>
<li><b>Related Patterns:</b> Other patterns that have some relationship with the pattern; discussion of the differences between the pattern and similar patterns.</li></ul>
<div class="mw-heading mw-heading2"><h2 id="Criticism">Criticism</h2></div>
<p>Some suggest that design patterns may be a sign that features are missing in a given programming language (<a href="Java_(programming_language)" title="Java (programming language)">Java</a> or <a href="C%2B%2B" title="C++">C++</a> for instance). <a href="Peter_Norvig" title="Peter Norvig">Peter Norvig</a> demonstrates that 16 out of the 23 patterns in the <i>Design Patterns</i> book (which is primarily focused on C++) are simplified or eliminated (via direct language support) in <a href="Lisp_(programming_language)" title="Lisp (programming language)">Lisp</a> or <a href="Dylan_(programming_language)" title="Dylan (programming language)">Dylan</a>.<sup id="cite_ref-Norvig1998_29-0" class="reference"><a href="#cite_note-Norvig1998-29"><span class="cite-bracket">[</span>29<span class="cite-bracket">]</span></a></sup> Related observations were made by Hannemann and Kiczales who implemented several of the 23 design patterns using an <a href="Aspect-oriented_programming" title="Aspect-oriented programming">aspect-oriented programming language</a> (AspectJ) and showed that code-level dependencies were removed from the implementations of 17 of the 23 design patterns and that aspect-oriented programming could simplify the implementations of design patterns.<sup id="cite_ref-Hannemann2002_30-0" class="reference"><a href="#cite_note-Hannemann2002-30"><span class="cite-bracket">[</span>30<span class="cite-bracket">]</span></a></sup>
See also <a href="Paul_Graham_(computer_programmer)" class="mw-redirect" title="Paul Graham (computer programmer)">Paul Graham's</a> essay "Revenge of the Nerds".<sup id="cite_ref-Graham2002_31-0" class="reference"><a href="#cite_note-Graham2002-31"><span class="cite-bracket">[</span>31<span class="cite-bracket">]</span></a></sup>
</p><p>Inappropriate use of patterns may unnecessarily increase complexity.<sup id="cite_ref-CodeComplete2_32-0" class="reference"><a href="#cite_note-CodeComplete2-32"><span class="cite-bracket">[</span>32<span class="cite-bracket">]</span></a></sup> <a rel="nofollow" class="external text" href="https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition">FizzBuzzEnterpriseEdition</a> offers a humorous example of over-complexity introduced by design patterns.<sup id="cite_ref-Kragbæk2016_33-0" class="reference"><a href="#cite_note-Kragbæk2016-33"><span class="cite-bracket">[</span>33<span class="cite-bracket">]</span></a></sup>
</p><p>By definition, a pattern must be programmed anew into each application that uses it. Since some authors see this as a step backward from <a href="Software_reuse" class="mw-redirect" title="Software reuse">software reuse</a> as provided by <a href="Software_componentry" class="mw-redirect" title="Software componentry">components</a>, researchers have worked to turn patterns into components. Meyer and Arnout were able to provide full or partial componentization of two-thirds of the patterns they attempted.<sup id="cite_ref-Meyer2006_34-0" class="reference"><a href="#cite_note-Meyer2006-34"><span class="cite-bracket">[</span>34<span class="cite-bracket">]</span></a></sup>
</p><p>In order to achieve flexibility, design patterns may introduce additional levels of <a href="Indirection" title="Indirection">indirection</a>, which may complicate the resulting design and decrease <a href="Runtime_(program_lifecycle_phase)" class="mw-redirect" title="Runtime (program lifecycle phase)">runtime</a> performance.
</p><p><br>
</p>
<div class="mw-heading mw-heading2"><h2 id="Relationship_to_other_topics">Relationship to other topics</h2></div>
<p>Software design patterns offer finer granularity compared to software architecture patterns and software architecture styles, as design patterns focus on solving detailed, low-level design problems within individual components or subsystems. Examples include Singleton, Factory Method, and Observer. <sup id="cite_ref-O'Reilly_Media_35-0" class="reference"><a href="#cite_note-O'Reilly_Media-35"><span class="cite-bracket">[</span>35<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:0_36-0" class="reference"><a href="#cite_note-:0-36"><span class="cite-bracket">[</span>36<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:1_37-0" class="reference"><a href="#cite_note-:1-37"><span class="cite-bracket">[</span>37<span class="cite-bracket">]</span></a></sup>
</p><p><a href="List_of_software_architecture_styles_and_patterns" title="List of software architecture styles and patterns">Software Architecture Pattern</a> refers to a reusable, proven solution to a recurring problem at the system level, addressing concerns related to the overall structure, component interactions, and quality attributes of the system. Software architecture patterns operate at a higher level of abstraction than design patterns, solving broader system-level challenges. While these patterns typically affect system-level concerns, the distinction between architectural patterns and architectural styles can sometimes be blurry. Examples include <a href="Circuit_breaker_design_pattern" title="Circuit breaker design pattern">Circuit Breaker</a>. <sup id="cite_ref-O'Reilly_Media_35-1" class="reference"><a href="#cite_note-O'Reilly_Media-35"><span class="cite-bracket">[</span>35<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:0_36-1" class="reference"><a href="#cite_note-:0-36"><span class="cite-bracket">[</span>36<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:1_37-1" class="reference"><a href="#cite_note-:1-37"><span class="cite-bracket">[</span>37<span class="cite-bracket">]</span></a></sup>
</p><p><a href="List_of_software_architecture_styles_and_patterns" title="List of software architecture styles and patterns">Software Architecture Style</a> refers to a high-level structural organization that defines the overall system organization, specifying how components are organized, how they interact, and the constraints on those interactions. Architecture styles typically include a vocabulary of component and connector types, as well as semantic models for interpreting the system's properties. These styles represent the most coarse-grained level of system organization. Examples include <a href="Multitier_architecture" title="Multitier architecture">Layered Architecture</a>, <a href="Microservices" title="Microservices">Microservices</a>, and <a href="Event-driven_architecture" title="Event-driven architecture">Event-Driven Architecture</a>. <sup id="cite_ref-O'Reilly_Media_35-2" class="reference"><a href="#cite_note-O'Reilly_Media-35"><span class="cite-bracket">[</span>35<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:0_36-2" class="reference"><a href="#cite_note-:0-36"><span class="cite-bracket">[</span>36<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:1_37-2" class="reference"><a href="#cite_note-:1-37"><span class="cite-bracket">[</span>37<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1184024115">
/* start https://en.wikipedia.org/ */
.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}
/* end https://en.wikipedia.org/ */
</style><div class="div-col" style="column-width: 22em;">
<ul><li><a href="Abstraction_principle_(programming)" class="mw-redirect" title="Abstraction principle (programming)">Abstraction principle</a></li>
<li><a href="Algorithmic_skeleton" title="Algorithmic skeleton">Algorithmic skeleton</a></li>
<li><a href="Anti-pattern" title="Anti-pattern">Anti-pattern</a></li>
<li><a href="Architectural_pattern" title="Architectural pattern">Architectural pattern</a></li>
<li><a href="Canonical_protocol_pattern" title="Canonical protocol pattern">Canonical protocol pattern</a></li>
<li><a href="Debugging_patterns" class="mw-redirect" title="Debugging patterns">Debugging patterns</a></li>
<li><a href="Design_pattern" title="Design pattern">Design pattern</a></li>
<li><a href="Distributed_design_patterns" title="Distributed design patterns">Distributed design patterns</a></li>
<li>Double-chance function</li>
<li><a href="Enterprise_Architecture_framework" class="mw-redirect" title="Enterprise Architecture framework">Enterprise Architecture framework</a></li>
<li><a href="GRASP_(object-oriented_design)" title="GRASP (object-oriented design)">GRASP (object-oriented design)</a></li>
<li><a href="Helper_class" title="Helper class">Helper class</a></li>
<li><a href="Programming_idiom" title="Programming idiom">Idiom</a> in programming</li>
<li><a href="Interaction_design_pattern" title="Interaction design pattern">Interaction design pattern</a></li>
<li><a href="List_of_software_architecture_styles_and_patterns" title="List of software architecture styles and patterns">List of software architecture styles and patterns</a></li>
<li><a href="List_of_software_development_philosophies" title="List of software development philosophies">List of software development philosophies</a></li>
<li><a href="List_of_software_engineering_topics" class="mw-redirect" title="List of software engineering topics">List of software engineering topics</a></li>
<li><a href="Pattern_language" title="Pattern language">Pattern language</a></li>
<li><a href="Pattern_theory" title="Pattern theory">Pattern theory</a></li>
<li><a href="Pedagogical_patterns" class="mw-redirect" title="Pedagogical patterns">Pedagogical patterns</a></li>
<li><a href="Portland_Pattern_Repository" title="Portland Pattern Repository">Portland Pattern Repository</a></li>
<li><a href="Refactoring" class="mw-redirect" title="Refactoring">Refactoring</a></li>
<li><a href="Software_development_methodology" class="mw-redirect" title="Software development methodology">Software development methodology</a></li></ul>
</div>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */
.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}
/* end https://en.wikipedia.org/ */
</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">
<ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><cite id="CITEREFAlexandrescu2001" class="citation book cs1">Alexandrescu, Andrei (2001). <i>Modern C++ Design: Generic Programming and Design Patterns Applied</i>. Addison-Wesley. p. xviii. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-70431-0</bdi>.</cite></span>
</li>
<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFHorner2005" class="citation book cs1">Horner, Mark (2005). "9". <i>Pro .NET 2.0 Code and Design Standards in C#</i>. Apress. p. 171. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-59059-560-2</bdi>.</cite></span>
</li>
<li id="cite_note-Smith1987-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-Smith1987_3-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFSmith1987" class="citation conference cs1">Smith, Reid (October 1987). <i>Panel on design methodology</i>. <a href="OOPSLA" title="OOPSLA">OOPSLA</a> '87 Addendum to the Proceedings. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F62138.62151">10.1145/62138.62151</a>. <q>Ward cautioned against requiring too much programming at, what he termed, 'the high level of wizards.' He pointed out that a written 'pattern language' can significantly improve the selection and application of abstractions. He proposed a 'radical shift in the burden of design and implementation' basing the new methodology on an adaptation of Christopher Alexander's work in pattern languages and that programming-oriented pattern languages developed at <a href="Tektronix" title="Tektronix">Tektronix</a> has significantly aided their software development efforts.</q></cite></span>
</li>
<li id="cite_note-Beck1987-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-Beck1987_4-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFBeckCunningham1987" class="citation conference cs1"><a href="Kent_Beck" title="Kent Beck">Beck, Kent</a>; <a href="Ward_Cunningham" title="Ward Cunningham">Cunningham, Ward</a> (September 1987). <a rel="nofollow" class="external text" href="http://c2.com/doc/oopsla87.html"><i>Using Pattern Languages for Object-Oriented Program</i></a>. <a href="OOPSLA" title="OOPSLA">OOPSLA</a> '87 workshop on <i>Specification and Design for Object-Oriented Programming</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2006-05-26</span></span>.</cite></span>
</li>
<li id="cite_note-Baroni2003-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-Baroni2003_5-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFBaroniGuéhéneucAlbin-Amiot2003" class="citation report cs1">Baroni, Aline Lúcia; Guéhéneuc, Yann-Gaël; Albin-Amiot, Hervé (June 2003). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/277282980">Design Patterns Formalization</a> (Report). EMN Technical Report. <a href="Nantes" title="Nantes">Nantes</a>: École Nationale Supérieure des Techniques Industrielles et des Mines de Nantes. <a href="CiteSeerX_(identifier)" class="mw-redirect" title="CiteSeerX (identifier)">CiteSeerX</a> <span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.62.6466">10.1.1.62.6466</a></span>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:624834">624834</a> – via ResearchGate.</cite></span>
</li>
<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite id="CITEREFBishop" class="citation web cs1">Bishop, Judith. <a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/vstudio/ff729657">"C# 3.0 Design Patterns: Use the Power of C# 3.0 to Solve Real-World Problems"</a>. C# Books from O'Reilly Media<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-05-15</span></span>. <q>If you want to speed up the development of your .NET applications, you're ready for C# design patterns -- elegant, accepted and proven ways to tackle common programming problems.</q></cite></span>
</li>
<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite id="CITEREFTiako2009" class="citation book cs1">Tiako, Pierre F. (31 March 2009). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=_SklFgSidxQC&q=Reusing+design+patterns+helps+to+prevent+such+subtle+issues&pg=PA636">"Formal Modeling and Specification of Design Patterns Using RTPA"</a>. In Tiako, Pierre F (ed.). <i>Software Applications: Concepts, Methodologies, Tools, and Applications: Concepts, Methodologies, Tools, and Applications</i>. p. 636. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.4018%2F978-1-60566-060-8">10.4018/978-1-60566-060-8</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781605660615</bdi>.</cite></span>
</li>
<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite id="CITEREFLaakso2003" class="citation web cs1">Laakso, Sari A. (2003-09-16). <a rel="nofollow" class="external text" href="http://www.cs.helsinki.fi/u/salaakso/patterns/index.html">"Collection of User Interface Design Patterns"</a>. University of Helsinki, Dept. of Computer Science<span class="reference-accessdate">. Retrieved <span class="nowrap">2008-01-31</span></span>.</cite></span>
</li>
<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFHeerAgrawala2006" class="citation journal cs1">Heer, J.; Agrawala, M. (2006). <a rel="nofollow" class="external text" href="http://vis.berkeley.edu/papers/infovis_design_patterns/">"Software Design Patterns for Information Visualization"</a>. <i>IEEE Transactions on Visualization and Computer Graphics</i>. <b>12</b> (5): <span class="nowrap">853–</span>60. <a href="CiteSeerX_(identifier)" class="mw-redirect" title="CiteSeerX (identifier)">CiteSeerX</a> <span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.121.4534">10.1.1.121.4534</a></span>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTVCG.2006.178">10.1109/TVCG.2006.178</a>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/17080809">17080809</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:11634997">11634997</a>.</cite></span>
</li>
<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite id="CITEREFDoughertySayreSeacordSvoboda2009" class="citation book cs1">Dougherty, Chad; Sayre, Kirk; Seacord, Robert C.; Svoboda, David; Togashi, Kazuya (2009). <a rel="nofollow" class="external text" href="http://www.cert.org/archive/pdf/09tr010.pdf"><i>Secure Design Patterns</i></a> <span class="cs1-format">(PDF)</span>. Software Engineering Institute.</cite></span>
</li>
<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><cite id="CITEREFGarfinkel2005" class="citation thesis cs1">Garfinkel, Simson L. (2005). <a rel="nofollow" class="external text" href="http://www.simson.net/thesis/"><i>Design Principles and Patterns for Computer Systems That Are Simultaneously Secure and Usable</i></a> (Ph.D. thesis).</cite></span>
</li>
<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20080229011119/http://developer.yahoo.com/ypatterns/">"Yahoo! Design Pattern Library"</a>. Archived from <a rel="nofollow" class="external text" href="http://developer.yahoo.com/ypatterns/">the original</a> on 2008-02-29<span class="reference-accessdate">. Retrieved <span class="nowrap">2008-01-31</span></span>.</cite></span>
</li>
<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://torgronsund.wordpress.com/2010/01/06/lean-startup-business-model-pattern/">"How to design your Business Model as a Lean Startup?"</a>. 2010-01-06<span class="reference-accessdate">. Retrieved <span class="nowrap">2010-01-06</span></span>.</cite></span>
</li>
<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text">Pattern Languages of Programming, Conference proceedings (annual, 1994—) <a rel="nofollow" class="external autonumber" href="http://hillside.net/plop/pastconferences.html">[1]</a></span>
</li>
<li id="cite_note-McConnell2004-15"><span class="mw-cite-backlink">^ <a href="#cite_ref-McConnell2004_15-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-McConnell2004_15-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-McConnell2004_15-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFMcConnell2004" class="citation book cs1"><a href="Steve_McConnell" title="Steve McConnell">McConnell, Steve</a> (June 2004). "Design in Construction". <a href="Code_Complete" title="Code Complete"><i>Code Complete</i></a> (2nd ed.). <a href="Microsoft_Press" title="Microsoft Press">Microsoft Press</a>. p. <a rel="nofollow" class="external text" href="https://archive.org/details/codecomplete0000mcco/page/104">104</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-7356-1967-8</bdi>. <q>Table 5.1 Popular Design Patterns</q></cite></span>
</li>
<li id="cite_note-PoEAA-16"><span class="mw-cite-backlink">^ <a href="#cite_ref-PoEAA_16-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-PoEAA_16-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFFowler2002" class="citation book cs1"><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a> (2002). <a rel="nofollow" class="external text" href="http://martinfowler.com/books.html#eaa"><i>Patterns of Enterprise Application Architecture</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-12742-6</bdi>.</cite></span>
</li>
<li id="cite_note-J2EE_Patterns-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-J2EE_Patterns_17-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFAlurCrupiMalks2003" class="citation book cs1">Alur, Deepak; Crupi, John; Malks, Dan (2003). <a rel="nofollow" class="external text" href="http://www.corej2eepatterns.com"><i>Core J2EE Patterns: Best Practices and Design Strategies</i></a>. <a href="Prentice_Hall" title="Prentice Hall">Prentice Hall</a>. p. 166. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-142246-9</bdi>.</cite></span>
</li>
<li id="cite_note-PoEAA2-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-PoEAA2_18-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFFowler2002" class="citation book cs1"><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a> (2002). <a rel="nofollow" class="external text" href="http://martinfowler.com/books.html#eaa"><i>Patterns of Enterprise Application Architecture</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. p. 344. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-12742-6</bdi>.</cite></span>
</li>
<li id="cite_note-EffectiveJava-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-EffectiveJava_19-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFBloch2008" class="citation book cs1">Bloch, Joshua (2008). <a rel="nofollow" class="external text" href="https://archive.org/details/effectivejava00bloc_0/page/179">"Item 37: Use marker interfaces to define types"</a>. <i>Effective Java</i> (Second ed.). Addison-Wesley. p. <a rel="nofollow" class="external text" href="https://archive.org/details/effectivejava00bloc_0/page/179">179</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-35668-0</bdi>.</cite></span>
</li>
<li id="cite_note-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-20">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.ssw.jku.at/Research/Papers/Moe99/Paper.pdf">"Twin – A Design Pattern for Modeling Multiple Inheritance"</a> <span class="cs1-format">(PDF)</span>.</cite></span>
</li>
<li id="cite_note-POSA2-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-POSA2_21-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFSchmidtStalRohnertBuschmann2000" class="citation book cs1">Schmidt, Douglas C.; Stal, Michael; Rohnert, Hans; Buschmann, Frank (2000). <i>Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects</i>. John Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-471-60695-6</bdi>.</cite></span>
</li>
<li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://c2.com/cgi/wiki?BindingProperties">Binding Properties</a></span>
</li>
<li id="cite_note-PC#2008-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-PC#2008_23-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFNagelEvjenGlynnWatson2008" class="citation book cs1">Nagel, Christian; Evjen, Bill; Glynn, Jay; Watson, Karli; Skinner, Morgan (2008). "Event-based Asynchronous Pattern". <i>Professional C# 2008</i>. Wiley. pp. <span class="nowrap">570–</span>571. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-470-19137-8</bdi>.</cite></span>
</li>
<li id="cite_note-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-24">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://c2.com/cgi/wiki?LockPattern">Lock Pattern</a></span>
</li>
<li id="cite_note-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-25">^</a></b></span> <span class="reference-text"><cite id="CITEREFFrancalanzaTabone2023" class="citation journal cs1">Francalanza, Adrian; Tabone, Gerard (October 2023). "ElixirST: A session-based type system for Elixir modules". <i>Journal of Logical and Algebraic Methods in Programming</i>. <b>135</b>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.jlamp.2023.100891">10.1016/j.jlamp.2023.100891</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:251442539">251442539</a>.</cite></span>
</li>
<li id="cite_note-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-26">^</a></b></span> <span class="reference-text"><cite id="CITEREFSchmidtVinoski1996" class="citation journal cs1">Schmidt, Douglas C.; Vinoski, Steve (July–August 1996). <a rel="nofollow" class="external text" href="https://www.dre.vanderbilt.edu/~schmidt/PDF/C++-report-col7.pdf">"Object Interconnections: Comparing Alternative Programming Techniques for Multi-threaded CORBA Servers (Column 7)"</a> <span class="cs1-format">(PDF)</span>. <i>SIGS C++ Report</i>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:2654843">2654843</a>.</cite></span>
</li>
<li id="cite_note-GabrielHillside-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-GabrielHillside_27-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFGabriel" class="citation web cs1"><a href="Richard_P._Gabriel" title="Richard P. Gabriel">Gabriel, Dick</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070209224120/http://hillside.net/patterns/definition.html">"A Pattern Definition"</a>. Archived from <a rel="nofollow" class="external text" href="http://hillside.net/patterns/definition.html">the original</a> on 2007-02-09<span class="reference-accessdate">. Retrieved <span class="nowrap">2007-03-06</span></span>.</cite></span>
</li>
<li id="cite_note-Fowler2006-28"><span class="mw-cite-backlink"><b><a href="#cite_ref-Fowler2006_28-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFFowler2006" class="citation web cs1"><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a> (2006-08-01). <a rel="nofollow" class="external text" href="http://www.martinfowler.com/articles/writingPatterns.html">"Writing Software Patterns"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2007-03-06</span></span>.</cite></span>
</li>
<li id="cite_note-Norvig1998-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-Norvig1998_29-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFNorvig1998" class="citation conference cs1"><a href="Peter_Norvig" title="Peter Norvig">Norvig, Peter</a> (1998). <a rel="nofollow" class="external text" href="http://www.norvig.com/design-patterns/"><i>Design Patterns in Dynamic Languages</i></a>.</cite></span>
</li>
<li id="cite_note-Hannemann2002-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-Hannemann2002_30-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFHannemannKiczales2002" class="citation conference cs1">Hannemann, Jan; <a href="Gregor_Kiczales" title="Gregor Kiczales">Kiczales, Gregor</a> (2002). "Design pattern implementation in Java and AspectJ". <i>Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications - OOPSLA '02</i>. OOPSLA '02. p. 161. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F582419.582436">10.1145/582419.582436</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1581134711</bdi>.</cite></span>
</li>
<li id="cite_note-Graham2002-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-Graham2002_31-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFGraham2002" class="citation web cs1"><a href="Paul_Graham_(computer_programmer)" class="mw-redirect" title="Paul Graham (computer programmer)">Graham, Paul</a> (2002). <a rel="nofollow" class="external text" href="http://www.paulgraham.com/icad.html">"Revenge of the Nerds"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2012-08-11</span></span>.</cite></span>
</li>
<li id="cite_note-CodeComplete2-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-CodeComplete2_32-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFMcConnell2004" class="citation book cs1">McConnell, Steve (2004). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/codecomplete0000mcco"><i>Code Complete: A Practical Handbook of Software Construction, 2nd Edition</i></a></span>. Pearson Education. p. <a rel="nofollow" class="external text" href="https://archive.org/details/codecomplete0000mcco/page/105">105</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780735619678</bdi>.</cite></span>
</li>
<li id="cite_note-Kragbæk2016-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-Kragbæk2016_33-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFKragbæk" class="citation web cs1">Kragbæk, Mikael. <a rel="nofollow" class="external text" href="https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition">"FizzBuzzEnterpriseEdition"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2024-11-19</span></span>.</cite></span>
</li>
<li id="cite_note-Meyer2006-34"><span class="mw-cite-backlink"><b><a href="#cite_ref-Meyer2006_34-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFMeyerArnout2006" class="citation journal cs1"><a href="Bertrand_Meyer" title="Bertrand Meyer">Meyer, Bertrand</a>; Arnout, Karine (July 2006). <a rel="nofollow" class="external text" href="http://se.ethz.ch/~meyer/publications/computer/visitor.pdf">"Componentization: The Visitor Example"</a> <span class="cs1-format">(PDF)</span>. <i><a href="IEEE_Computer" class="mw-redirect" title="IEEE Computer">IEEE Computer</a></i>. <b>39</b> (7): <span class="nowrap">23–</span>30. <a href="CiteSeerX_(identifier)" class="mw-redirect" title="CiteSeerX (identifier)">CiteSeerX</a> <span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.62.6082">10.1.1.62.6082</a></span>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMC.2006.227">10.1109/MC.2006.227</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:15328522">15328522</a>.</cite></span>
</li>
<li id="cite_note-O'Reilly_Media-35"><span class="mw-cite-backlink">^ <a href="#cite_ref-O'Reilly_Media_35-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-O'Reilly_Media_35-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-O'Reilly_Media_35-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite class="citation book cs1"><i>Fundamentals of Software Architecture: An Engineering Approach</i>. O'Reilly Media. 2020. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1492043454</bdi>.</cite></span>
</li>
<li id="cite_note-:0-36"><span class="mw-cite-backlink">^ <a href="#cite_ref-:0_36-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:0_36-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:0_36-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite class="citation book cs1"><i>Design Patterns: Elements of Reusable Object-Oriented Software</i>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0201633610</bdi>.</cite></span>
</li>
<li id="cite_note-:1-37"><span class="mw-cite-backlink">^ <a href="#cite_ref-:1_37-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:1_37-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:1_37-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite class="citation book cs1"><i>Patterns of Enterprise Application Architecture</i>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0321127426</bdi>.</cite></span>
</li>
</ol></div>
<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239549316">
/* start https://en.wikipedia.org/ */
.mw-parser-output .refbegin{margin-bottom:0.5em}.mw-parser-output .refbegin-hanging-indents>ul{margin-left:0}.mw-parser-output .refbegin-hanging-indents>ul>li{margin-left:0;padding-left:3.2em;text-indent:-3.2em}.mw-parser-output .refbegin-hanging-indents ul,.mw-parser-output .refbegin-hanging-indents ul li{list-style:none}@media(max-width:720px){.mw-parser-output .refbegin-hanging-indents>ul>li{padding-left:1.6em;text-indent:-1.6em}}.mw-parser-output .refbegin-columns{margin-top:0.3em}.mw-parser-output .refbegin-columns ul{margin-top:0}.mw-parser-output .refbegin-columns li{page-break-inside:avoid;break-inside:avoid-column}@media screen{.mw-parser-output .refbegin{font-size:90%}}
/* end https://en.wikipedia.org/ */
</style><div class="refbegin" style="">
<ul><li><cite id="CITEREFAlexanderIshikawaSilversteinJacobson1977" class="citation book cs1"><a href="Christopher_Alexander" title="Christopher Alexander">Alexander, Christopher</a>; Ishikawa, Sara; Silverstein, Murray; Jacobson, Max; Fiksdahl-King, Ingrid; Angel, Shlomo (1977). <a href="A_Pattern_Language%3A_Towns%2C_Buildings%2C_Construction" class="mw-redirect" title="A Pattern Language: Towns, Buildings, Construction"><i>A Pattern Language: Towns, Buildings, Construction</i></a>. New York: Oxford University Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-19-501919-3</bdi>.</cite></li>
<li><cite id="CITEREFAlurCrupiMalks2003" class="citation book cs1">Alur, Deepak; Crupi, John; Malks, Dan (May 2003). <i>Core J2EE Patterns: Best Practices and Design Strategies</i> (2nd ed.). <a href="Prentice_Hall" title="Prentice Hall">Prentice Hall</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-142246-9</bdi>.</cite></li>
<li><cite id="CITEREFBeck2007" class="citation book cs1"><a href="Kent_Beck" title="Kent Beck">Beck, Kent</a> (October 2007). <i>Implementation Patterns</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-41309-3</bdi>.</cite></li>
<li><cite id="CITEREFBeckCrockerMeszarosCoplien1996" class="citation book cs1"><a href="Kent_Beck" title="Kent Beck">Beck, Kent</a>; Crocker, R.; Meszaros, G.; <a href="James_O._Coplien" class="mw-redirect" title="James O. Coplien">Coplien, J. O.</a>; Dominick, L.; Paulisch, F.; <a href="John_Vlissides" title="John Vlissides">Vlissides, J.</a> (March 1996). <i>Proceedings of the 18th International Conference on Software Engineering</i>. pp. <span class="nowrap">25–</span>30.</cite></li>
<li><cite id="CITEREFBorchers2001" class="citation book cs1">Borchers, Jan (2001). <i>A Pattern Approach to Interaction Design</i>. <a href="John_Wiley_%26_Sons" class="mw-redirect" title="John Wiley & Sons">John Wiley & Sons</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-471-49828-5</bdi>.</cite></li>
<li><cite id="CITEREFCoplienSchmidt1995" class="citation book cs1"><a href="Jim_Coplien" title="Jim Coplien">Coplien, James O.</a>; Schmidt, Douglas C. (1995). <i>Pattern Languages of Program Design</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-60734-5</bdi>.</cite></li>
<li><cite id="CITEREFCoplienVlissidesKerth1996" class="citation book cs1"><a href="Jim_Coplien" title="Jim Coplien">Coplien, James O.</a>; <a href="John_Vlissides" title="John Vlissides">Vlissides, John M.</a>; Kerth, Norman L. (1996). <i>Pattern Languages of Program Design 2</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-89527-8</bdi>.</cite></li>
<li><cite id="CITEREFElorantaKoskinenLeppänenReijonen2014" class="citation book cs1">Eloranta, Veli-Pekka; Koskinen, Johannes; Leppänen, Marko; Reijonen, Ville (2014). <i>Designing Distributed Control Systems: A Pattern Language Approach</i>. Wiley. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1118694152</bdi>.</cite></li>
<li><cite id="CITEREFFowler1997" class="citation book cs1"><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a> (1997). <i>Analysis Patterns: Reusable Object Models</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-89542-1</bdi>.</cite></li>
<li><cite id="CITEREFFowler2003" class="citation book cs1"><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a> (2003). <i>Patterns of Enterprise Application Architecture</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-12742-6</bdi>.</cite></li>
<li><cite id="CITEREFFreemanFreemanSierraBates2004" class="citation book cs1">Freeman, Eric; Freeman, Elisabeth; <a href="Kathy_Sierra" title="Kathy Sierra">Sierra, Kathy</a>; Bates, Bert (2004). <i>Head First Design Patterns</i>. <a href="O'Reilly_Media" title="O'Reilly Media">O'Reilly Media</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-596-00712-6</bdi>.</cite></li>
<li><cite id="CITEREFHohmannFowlerKawasaki2003" class="citation book cs1">Hohmann, Luke; <a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a>; <a href="Guy_Kawasaki" title="Guy Kawasaki">Kawasaki, Guy</a> (2003). <i>Beyond Software Architecture</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-77594-5</bdi>.</cite></li>
<li><cite id="CITEREFGabriel1996" class="citation book cs1"><a href="Richard_P._Gabriel" title="Richard P. Gabriel">Gabriel, Richard</a> (1996). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20030801111358/http://dreamsongs.com/NewFiles/PatternsOfSoftware.pdf"><i>Patterns of Software: Tales From The Software Community</i></a> <span class="cs1-format">(PDF)</span>. <a href="Oxford_University_Press" title="Oxford University Press">Oxford University Press</a>. p. 235. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-19-512123-0</bdi>. Archived from <a rel="nofollow" class="external text" href="http://www.dreamsongs.com/NewFiles/PatternsOfSoftware.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2003-08-01.</cite></li>
<li><cite id="book_Gamma1995" class="citation book cs1"><a href="Erich_Gamma" title="Erich Gamma">Gamma, Erich</a>; <a href="Richard_Helm" title="Richard Helm">Helm, Richard</a>; <a href="Ralph_Johnson_(computer_scientist)" title="Ralph Johnson (computer scientist)">Johnson, Ralph</a>; <a href="John_Vlissides" title="John Vlissides">Vlissides, John</a> (1995). <a href="Design_Patterns_(book)" class="mw-redirect" title="Design Patterns (book)"><i>Design Patterns: Elements of Reusable Object-Oriented Software</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-63361-0</bdi>.</cite></li>
<li><cite id="CITEREFHohpeWoolf2003" class="citation book cs1">Hohpe, Gregor; Woolf, Bobby (2003). <a href="Enterprise_Integration_Patterns" title="Enterprise Integration Patterns"><i>Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-20068-6</bdi>.</cite></li>
<li><cite id="CITEREFHolub2004" class="citation book cs1">Holub, Allen (2004). <i>Holub on Patterns</i>. <a href="Apress" class="mw-redirect" title="Apress">Apress</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-59059-388-2</bdi>.</cite></li>
<li><cite id="CITEREFKircherVölterZdun2005" class="citation book cs1">Kircher, Michael; Völter, Markus; Zdun, Uwe (2005). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/remotingpatterns0000volt"><i>Remoting Patterns: Foundations of Enterprise, Internet and Realtime Distributed Object Middleware</i></a></span>. <a href="John_Wiley_%26_Sons" class="mw-redirect" title="John Wiley & Sons">John Wiley & Sons</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-470-85662-8</bdi>.</cite></li>
<li><cite id="CITEREFLarman2005" class="citation book cs1"><a href="Craig_Larman" title="Craig Larman">Larman, Craig</a> (2005). <i>Applying UML and Patterns</i>. <a href="Prentice_Hall" title="Prentice Hall">Prentice Hall</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-148906-6</bdi>.</cite></li>
<li><cite id="CITEREFLiskovGuttag2000" class="citation book cs1"><a href="Barbara_Liskov" title="Barbara Liskov">Liskov, Barbara</a>; <a href="John_Guttag" title="John Guttag">Guttag, John</a> (2000). <i>Program Development in Java: Abstraction, Specification, and Object-Oriented Design</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-65768-5</bdi>.</cite></li>
<li><cite id="CITEREFManolescuVoelterNoble2006" class="citation book cs1">Manolescu, Dragos; Voelter, Markus; Noble, James (2006). <i>Pattern Languages of Program Design 5</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-32194-7</bdi>.</cite></li>
<li><cite id="CITEREFMarinescu2002" class="citation book cs1">Marinescu, Floyd (2002). <a rel="nofollow" class="external text" href="https://archive.org/details/ejbdesignpattern00mari"><i>EJB Design Patterns: Advanced Patterns, Processes and Idioms</i></a>. <a href="John_Wiley_%26_Sons" class="mw-redirect" title="John Wiley & Sons">John Wiley & Sons</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-471-20831-0</bdi>.</cite></li>
<li><cite id="CITEREFMartinRiehleBuschmann1997" class="citation book cs1"><a href="Robert_C._Martin" title="Robert C. Martin">Martin, Robert Cecil</a>; Riehle, Dirk; Buschmann, Frank (1997). <i>Pattern Languages of Program Design 3</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-31011-5</bdi>.</cite></li>
<li><cite id="CITEREFMattsonSandersMassingill2005" class="citation book cs1">Mattson, Timothy G.; Sanders, Beverly A.; Massingill, Berna L. (2005). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/patternsforparal0000matt"><i>Patterns for Parallel Programming</i></a></span>. Addison-Wesley. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-22811-6</bdi>.</cite></li>
<li><cite id="CITEREFShallowayTrott2001" class="citation book cs1">Shalloway, Alan; Trott, James R. (2001). <a rel="nofollow" class="external text" href="https://archive.org/details/isbn_9780321247148"><i>Design Patterns Explained, Second Edition: A New Perspective on Object-Oriented Design</i></a>. Addison-Wesley. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-24714-8</bdi>.</cite></li>
<li><cite id="CITEREFVlissides1998" class="citation book cs1"><a href="John_Vlissides" title="John Vlissides">Vlissides, John M.</a> (1998). <i>Pattern Hatching: Design Patterns Applied</i>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-43293-0</bdi>.</cite></li>
<li><cite id="CITEREFWeirNoble2000" class="citation book cs1">Weir, Charles; Noble, James (2000). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070617114432/http://www.cix.co.uk/~smallmemory"><i>Small Memory Software: Patterns for systems with limited memory</i></a>. <a href="Addison-Wesley" title="Addison-Wesley">Addison-Wesley</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-201-59607-6</bdi>. Archived from <a rel="nofollow" class="external text" href="http://www.cix.co.uk/~smallmemory/">the original</a> on 2007-06-17.</cite></li></ul>
</div>
<div class="navbox-styles"><style data-mw-deduplicate="TemplateStyles:r1129693374">
/* start https://en.wikipedia.org/ */
.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}
/* end https://en.wikipedia.org/ */
</style><style data-mw-deduplicate="TemplateStyles:r1236075235">
/* start https://en.wikipedia.org/ */
.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}
/* end https://en.wikipedia.org/ */
</style></div><div role="navigation" class="navbox" aria-labelledby="Software_design_patterns225" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">
/* start https://en.wikipedia.org/ */
.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}
/* end https://en.wikipedia.org/ */
</style><div id="Software_design_patterns225" style="font-size:114%;margin:0 4em"></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Design_Patterns" title="Design Patterns">Gang of Four<br>patterns</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Creational_pattern" title="Creational pattern">Creational</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Abstract_factory_pattern" title="Abstract factory pattern">Abstract factory</a></li>
<li><a href="Builder_pattern" title="Builder pattern">Builder</a></li>
<li><a href="Factory_method_pattern" title="Factory method pattern">Factory method</a></li>
<li><a href="Prototype_pattern" title="Prototype pattern">Prototype</a></li>
<li><a href="Singleton_pattern" title="Singleton pattern">Singleton</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Structural_pattern" title="Structural pattern">Structural</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Adapter_pattern" title="Adapter pattern">Adapter</a></li>
<li><a href="Bridge_pattern" title="Bridge pattern">Bridge</a></li>
<li><a href="Composite_pattern" title="Composite pattern">Composite</a></li>
<li><a href="Decorator_pattern" title="Decorator pattern">Decorator</a></li>
<li><a href="Facade_pattern" title="Facade pattern">Facade</a></li>
<li><a href="Flyweight_pattern" title="Flyweight pattern">Flyweight</a></li>
<li><a href="Proxy_pattern" title="Proxy pattern">Proxy</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Behavioral_pattern" title="Behavioral pattern">Behavioral</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Chain-of-responsibility_pattern" title="Chain-of-responsibility pattern">Chain of responsibility</a></li>
<li><a href="Command_pattern" title="Command pattern">Command</a></li>
<li><a href="Interpreter_pattern" title="Interpreter pattern">Interpreter</a></li>
<li><a href="Iterator_pattern" title="Iterator pattern">Iterator</a></li>
<li><a href="Mediator_pattern" title="Mediator pattern">Mediator</a></li>
<li><a href="Memento_pattern" title="Memento pattern">Memento</a></li>
<li><a href="Observer_pattern" title="Observer pattern">Observer</a></li>
<li><a href="State_pattern" title="State pattern">State</a></li>
<li><a href="Strategy_pattern" title="Strategy pattern">Strategy</a></li>
<li><a href="Template_method_pattern" title="Template method pattern">Template method</a></li>
<li><a href="Visitor_pattern" title="Visitor pattern">Visitor</a></li></ul>
</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Concurrency_pattern" title="Concurrency pattern">Concurrency<br>patterns</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Active_object" title="Active object">Active object</a></li>
<li><a href="Balking_pattern" title="Balking pattern">Balking</a></li>
<li><a href="Binding_properties_pattern" title="Binding properties pattern">Binding properties</a></li>
<li><a href="Double-checked_locking" title="Double-checked locking">Double-checked locking</a></li>
<li><a href="Asynchronous_method_invocation" title="Asynchronous method invocation">Event-based asynchronous</a></li>
<li><a href="Guarded_suspension" title="Guarded suspension">Guarded suspension</a></li>
<li><a href="Join-pattern" title="Join-pattern">Join</a></li>
<li><a href="Lock_(computer_science)" title="Lock (computer science)">Lock</a></li>
<li><a href="Monitor_(synchronization)" title="Monitor (synchronization)">Monitor</a></li>
<li><a href="Proactor_pattern" title="Proactor pattern">Proactor</a></li>
<li><a href="Reactor_pattern" title="Reactor pattern">Reactor</a></li>
<li><a href="Readers%E2%80%93writer_lock" title="Readers–writer lock">Read–write lock</a></li>
<li><a href="Scheduler_pattern" class="mw-redirect" title="Scheduler pattern">Scheduler</a></li>
<li><a href="Scheduled-task_pattern" title="Scheduled-task pattern">Scheduled-task pattern</a></li>
<li><a href="Semaphore_(programming)" title="Semaphore (programming)">Semaphore</a></li>
<li><a href="Thread_pool" title="Thread pool">Thread pool</a></li>
<li><a href="Thread-local_storage" title="Thread-local storage">Thread-local storage</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Architectural_pattern" title="Architectural pattern">Architectural<br>patterns</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Front_controller" title="Front controller">Front controller</a></li>
<li><a href="Interceptor_pattern" title="Interceptor pattern">Interceptor</a></li>
<li><a href="Model%E2%80%93view%E2%80%93controller" title="Model–view–controller">MVC</a>
<ul><li><a href="Model%E2%80%93view%E2%80%93presenter" title="Model–view–presenter">MVP</a></li>
<li><a href="Model%E2%80%93view%E2%80%93viewmodel" title="Model–view–viewmodel">MVVM</a></li></ul></li>
<li><a href="Action%E2%80%93domain%E2%80%93responder" title="Action–domain–responder">ADR</a></li>
<li><a href="Entity_component_system" title="Entity component system">ECS</a></li>
<li><a href="Multitier_architecture" title="Multitier architecture"><i>n</i>-tier</a></li>
<li><a href="Specification_pattern" title="Specification pattern">Specification</a></li>
<li><a href="Publish%E2%80%93subscribe_pattern" title="Publish–subscribe pattern">Publish–subscribe</a></li>
<li><a href="Naked_objects" title="Naked objects">Naked objects</a></li>
<li><a href="Service_locator_pattern" title="Service locator pattern">Service locator</a></li>
<li><a href="Active_record_pattern" title="Active record pattern">Active record</a></li>
<li><a href="Identity_map_pattern" title="Identity map pattern">Identity map</a></li>
<li><a href="Data_access_object" title="Data access object">Data access object</a></li>
<li><a href="Data_transfer_object" title="Data transfer object">Data transfer object</a></li>
<li><a href="Inversion_of_control" title="Inversion of control">Inversion of control</a></li>
<li><a href="JSP_model_2_architecture" title="JSP model 2 architecture">Model 2</a></li>
<li><a href="Broker_pattern" title="Broker pattern">Broker</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other<br>patterns</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Blackboard_design_pattern" class="mw-redirect" title="Blackboard design pattern">Blackboard</a></li>
<li><a href="Business_delegate_pattern" title="Business delegate pattern">Business delegate</a></li>
<li><a href="Composite_entity_pattern" title="Composite entity pattern">Composite entity</a></li>
<li><a href="Dependency_injection" title="Dependency injection">Dependency injection</a></li>
<li><a href="Guard_(computer_science)" title="Guard (computer science)">Guard clause</a></li>
<li><a href="Intercepting_filter_pattern" title="Intercepting filter pattern">Intercepting filter</a></li>
<li><a href="Lazy_loading" title="Lazy loading">Lazy loading</a></li>
<li><a href="Mock_object" title="Mock object">Mock object</a></li>
<li><a href="Null_object_pattern" title="Null object pattern">Null object</a></li>
<li><a href="Object_pool_pattern" title="Object pool pattern">Object pool</a></li>
<li><a href="Servant_(design_pattern)" title="Servant (design pattern)">Servant</a></li>
<li><a href="Twin_pattern" title="Twin pattern">Twin</a></li>
<li><a href="Type_Tunnel_pattern" class="mw-redirect" title="Type Tunnel pattern">Type tunnel</a></li>
<li><a href="Method_chaining" title="Method chaining">Method chaining</a></li>
<li><a href="Delegation_pattern" title="Delegation pattern">Delegation</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Books</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><i><a href="Design_Patterns" title="Design Patterns">Design Patterns</a></i></li>
<li><i><a href="Enterprise_Integration_Patterns" title="Enterprise Integration Patterns">Enterprise Integration Patterns</a></i></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">People</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Christopher_Alexander" title="Christopher Alexander">Christopher Alexander</a></li>
<li><a href="Erich_Gamma" title="Erich Gamma">Erich Gamma</a></li>
<li><a href="Ralph_Johnson_(computer_scientist)" title="Ralph Johnson (computer scientist)">Ralph Johnson</a></li>
<li><a href="John_Vlissides" title="John Vlissides">John Vlissides</a></li>
<li><a href="Grady_Booch" title="Grady Booch">Grady Booch</a></li>
<li><a href="Kent_Beck" title="Kent Beck">Kent Beck</a></li>
<li><a href="Ward_Cunningham" title="Ward Cunningham">Ward Cunningham</a></li>
<li><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Martin Fowler</a></li>
<li><a href="Robert_C._Martin" title="Robert C. Martin">Robert Martin</a></li>
<li><a href="Jim_Coplien" title="Jim Coplien">Jim Coplien</a></li>
<li><a href="Douglas_C._Schmidt" title="Douglas C. Schmidt">Douglas Schmidt</a></li>
<li><a href="Linda_Rising" title="Linda Rising">Linda Rising</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Communities</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="The_Hillside_Group" title="The Hillside Group">The Hillside Group</a></li>
<li><a href="Portland_Pattern_Repository" title="Portland Pattern Repository">Portland Pattern Repository</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">See also</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Anti-pattern" title="Anti-pattern">Anti-pattern</a></li>
<li><a href="Architectural_pattern" title="Architectural pattern">Architectural pattern</a></li></ul>
</div></td></tr></tbody></table></div>
<div class="navbox-styles"></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q181156#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata799" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q181156#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata799" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4546895-3">Germany</a></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh98003823">United States</a></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://datos.bne.es/resource/XX550686">Spain</a></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007532683705171">Israel</a></span></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/0cb2920d-a952-4a14-9bd7-2edae9511abf">Yale LUX</a></span></li></ul></div></td></tr></tbody></table></div></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2025-08-05" href="https://en.wikipedia.org/wiki/?title=Software_design_pattern&oldid=1304300621">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>
</body></html>